chore(deps): update ghcr.io/google/yamlfmt docker tag to v0.17.2 #119
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.17.0->0.17.2Release Notes
google/yamlfmt (ghcr.io/google/yamlfmt)
v0.17.2Compare Source
Bug Fixes
Alias nodes no longer come with an extra whitespace
In an attempt to fix a behaviour in
yaml.v3's default encoding behaviour that would produce invalid YAML what an alias was used as a key (see #242) I introduced a regression where my fix was too wide of a net and produced an additional whitespace in scenarios where it wasn't necessary (see #250). To the extent of my testing this appears to be fixed now, however if that is not the case please feel free to re-open #250 with the example case that isn't covered or open a new issue.Contributors
Thank you @octo for the bug fix in #260!
v0.17.1Compare Source
Made this patch release because I don't have any upcoming work planned on
yamlfmtat the moment and wanted to get this bugfix released.Bug Fixes
yaml files with just comments had their contents erased.
If a yaml file had just comments, previously yamlfmt would erase the contents. This was an oversight on how
yaml.v3parses a file like this. Comment parsing works such that any comments found are attached as head, line, or foot comments to a given node. Since a yaml file with just comments has no nodes, the comment wouldn't be anywhere in the parse tree because the parse tree would be empty. Empty parse tree = yamlfmt produces an empty document. This is now properly treated as an edge case and will retain the contents as originally passed in if the file is just comments.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled because a matching PR was automerged previously.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.